Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1357

reference
299-tree-1
name
1357
tree-preservation-order

undefined

299-tpo-1
uprn
address-text
point
POINT (-1.027375 50.893439)
geometry
MULTIPOLYGON (((-1.027318 50.893432,-1.027321 50.893444,-1.027328 50.893454,-1.027341 50.893462,-1.027357 50.893467,-1.027374 50.893469,-1.027392 50.893467,-1.027408 50.893462,-1.027420 50.893454,-1.027429 50.893445,-1.027432 50.893433,-1.027429 50.893422,-1.027421 50.893412,-1.027409 50.893404,-1.027393 50.893399,-1.027376 50.893397,-1.027358 50.893399,-1.027342 50.893404,-1.027329 50.893411,-1.027321 50.893421,-1.027318 50.893432)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL